@pombredanne two test cases are failing when I used AssemblyVersion for
test_win_pe_Moq_Silverlight_dll and
test_win_pe_microsoft_practices_enterpriselibrary_caching_dll in test_win_pe.py

it shows (I checked for test_win_pe_Moq_Silverlight_dll)

>       assert result == expected
E       AssertionError: assert {'AssemblyVer...y': None, ...} == {'AssemblyVer...y': None, ...}
E
E         Omitting 20 identical items, use -vv to show
E         Differing items:
E         {'extra_data': {'Assembly Version': '4.2.1507.118'}} != {'extra_data': {}}
E         Use -v to get more diff

it shows that the result dictionary contains an extra_data field with {'Assembly Version': '4.2.1507.118'} that means extra_data field contains Assembly Version.

I think no need to change this 'Assembly Version' to 'AssemblyVersion' because extra_data field already contains
Assembly Version.

I think we should not handle the correct Windows PE versions when we using AssemblyVersion in #3790.
@pombredanne Am I Right??

Hey @pombredanne

You cannot replace one with the other, if need be you need both, if you can find a tiny test PE that actually contains "AssemblyVersion".

I use both "Assembly Version" and "AssemblyVersion" Now it is working and also all test cases are passed.

@alok1304 see #4116 (review) you need to add a minimal test with a real example to test this functionality. Look for test files similar to what we have, do you need any help finding these?

Look for test files similar to what we have, do you need any help finding these?

yes, I need help, how do we find these files for the test that contains AssemblyVersion?